Network slice customer (NSC) service ID and user equipment (UE) route selection policy (URSP)

ABSTRACT

A user equipment (UE) can operate to configure an application service to a network slice instance while preserving an application identity (ID) privacy. The UE receives network slice customer (NSC) Service ID from an NSC. A UE route selection policy (URSP) from a network slice provider (NSP), or network operator, includes the NSC Service ID in a traffic descriptor that associates a single network slice selection assistance information (S-NSSAI) with the NSC Service ID. The UE associates the application service to the network slice instance based on the NSC Service ID and the S-NSSAI.

CROSS-REFERENCE TO RELATED APPLICATIONS

The application claims the benefit of U.S. Provisional PatentApplication 63/059,708 filed Jul. 31, 2020, entitled “NETWORK SLICECUSTOMER (NSC) SERVICE ID AND USER EQUIPMENT (UE) ROUTE SELECTION POLICY(URSP)”, the contents of which are herein incorporated by reference intheir entirety.

FIELD

The present disclosure is in the field of wireless communications, andmore specifically, pertains to a network slice customer (NSC) serviceidentifier (ID) and a user equipment (UE) route selection policy (URSP).

BACKGROUND

Mobile communication in the next generation wireless communicationsystem, 5G, or new radio (NR) network will provide ubiquitousconnectivity and access to information, as well as ability to sharedata, around the globe. 5G networks and network slicing will be aunified, service-based framework that will target to meet versatile andsometimes, conflicting performance criteria and provide services tovastly heterogeneous application domains ranging from Enhanced MobileBroadband (eMBB) to massive Machine-Type Communications (mMTC),Ultra-Reliable Low-Latency Communications (URLLC), and othercommunications. In general, NR will evolve based on third generationpartnership project (3GPP) long term evolution (LTE)-Advanced technologywith additional enhanced radio access technologies (RATs) to enableseamless and faster wireless connectivity solutions. A concern innetwork slicing as a service (NSaaS) is ensuring user privacy while alsoenabling policy management operations are seamless for data traffic inorder to meet the demand for increase in traffic for larger bandwidth,lower latency, and higher data rates.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an exemplary block diagram illustrating an example of userequipment(s) (UEs) communicatively coupled a network with networkcomponents as peer devices useable in connection with various aspectsdescribed herein.

FIG. 2 is an exemplary a simplified block diagram of a user equipment(UE) wireless communication device or other network device/component(e.g., eNB, gNB) in accordance with various aspects.

FIG. 3 is an exemplary a block diagram of network slicing as a service(NSaaS) components in accordance with various aspects.

FIG. 4 is an exemplary data flow of network components for NSaaS inaccordance with various aspects.

FIG. 5 is an exemplary network slice customer (NSC) service ID inaccordance with various aspects.

FIG. 6 is an exemplary system diagram of network slicing as a service(NSaaS) components in accordance with various aspects.

FIG. 7 is another exemplary data flow of network components for NSaaSwith an NSC Service ID in accordance with various aspects.

FIG. 8 is another block diagram illustrating an example process flow fornetwork slicing according to various aspects.

FIG. 9 is another block diagram illustrating an example process flow fornetwork slicing according to various aspects.

FIG. 10 is another block diagram illustrating an example process flowfor network slicing according to various aspects.

DETAILED DESCRIPTION

It is well understood that the use of personally identifiableinformation should follow privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users. In particular,personally identifiable information data should be managed and handledso as to minimize risks of unintentional or unauthorized access or use,and the nature of authorized use should be clearly indicated to users.

The present disclosure will now be described with reference to theattached drawing figures, wherein like (or similarly ending) referencenumerals are used to refer to like elements throughout, and wherein theillustrated structures and devices are not necessarily drawn to scale.As utilized herein, terms “component,” “system,” “interface,” and thelike are intended to refer to a computer-related entity, hardware,software (e.g., in execution), and/or firmware. For example, a componentcan be a processor (e.g., a microprocessor, a controller, or otherprocessing device), a process running on a processor, a controller, anobject, an executable, a program, a storage device, a computer, a tabletPC and/or a user equipment (e.g., mobile phone, etc.) with a processingdevice. By way of illustration, an application running on a server andthe server can also be a component. One or more components can residewithin a process, and a component can be localized on one computerand/or distributed between two or more computers. A set of elements or aset of other components can be described herein, in which the term “set”can be interpreted as “one or more.”

Further, these components can execute from various computer readablestorage media having various data structures stored thereon such as witha module, for example. The components can communicate via local and/orremote processes such as in accordance with a signal having one or moredata packets (e.g., data from one component interacting with anothercomponent in a local system, distributed system, and/or across anetwork, such as, the Internet, a local area network, a wide areanetwork, or similar network with other systems via the signal).

As another example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, in which the electric or electronic circuitry canbe operated by a software application or a firmware application executedby one or more processors. The one or more processors can be internal orexternal to the apparatus and can execute at least a part of thesoftware or firmware application. As yet another example, a componentcan be an apparatus that provides specific functionality throughelectronic components without mechanical parts; the electroniccomponents can include one or more processors therein to executesoftware and/or firmware that confer(s), at least in part, thefunctionality of the electronic components.

Use of the word exemplary is intended to present concepts in a concretefashion. As used in this application, the term “or” is intended to meanan inclusive “or” rather than an exclusive “or”. That is, unlessspecified otherwise, or clear from context, “X employs A or B” isintended to mean any of the natural inclusive permutations. That is, ifX employs A; X employs B; or X employs both A and B, then “X employs Aor B” is satisfied under any of the foregoing instances. In addition,the articles “a” and “an” as used in this application and the appendedclaims should generally be construed to mean “one or more” unlessspecified otherwise or clear from context to be directed to a singularform. Furthermore, to the extent that the terms “including”, “includes”,“having”, “has”, “with”, or variants thereof are used in either thedetailed description and the claims, such terms are intended to beinclusive in a manner similar to the term “comprising.” Additionally, insituations wherein one or more numbered items are discussed (e.g., a“first X”, a “second X”, etc.), in general the one or more numbereditems can be distinct or they can be the same, although in somesituations the context can indicate that they are distinct or that theyare the same.

As used herein, the term “circuitry” can refer to, be part of, orinclude an Application Specific Integrated Circuit (ASIC), an electroniccircuit, a processor (shared, dedicated, or group), or associated memory(shared, dedicated, or group) operably coupled to the circuitry thatexecute one or more software or firmware programs, a combinational logiccircuit, or other suitable hardware components that provide thedescribed functionality. In some embodiments, the circuitry can beimplemented in, or functions associated with the circuitry can beimplemented by, one or more software or firmware modules. In someembodiments, circuitry can include logic, at least partially operable inhardware.

In consideration of various concerns for ensuring user privacy and datatraffic management, a traffic descriptor can be configured to enable anetwork device (e.g., an end user device, user equipment (UE), basestation, next generation NodeB (gNB), eNB, core network component, orother network component) to link a particular application service to adesignated network slice (network slice instance) without impacting userprivacy. In particular, a UE can receive a network slice customer (NSC)Service ID from an NSC such as a service provider of an application,wireless service, 3GPP provider, or the like. The NSC Service ID canidentifier the NSC with a particular service once the NSC has obtainedor received assignment to a network slice or network slice instance forcontrol and management. The UE can further receive a UE route selectionpolicy (URSP) with a traffic descriptor comprising the NSC Service ID ora component thereof and a rule that associates the NSC Service ID with asingle network slice selection assistance information (S-NSSAI) for thenetwork slice instance. The UE can then route data for an applicationwith an application ID to the network slice assigned to the NSC for theparticular service associated with the NSC Service ID of the NSC.Additional aspects and details of the disclosure are further describedbelow with reference to figures.

FIG. 1 illustrates an architecture of a system 100 with variouscomponents including a core network (CN) 120 in accordance with variousembodiments. The system 100 components can include a user equipment (UE)101, which can be the same or similar to other UEs discussed herein; aradio access network (R)AN 110 or access node (AN); and a data network(DN) 103, which can be, for example, operator services, Internet accessor 3rd party services, and a 5GC 120. The 5GC 120 can include anAuthentication Server Function (AUSF) 122; an Access and MobilityFunction (AMF) 121; a Session Management Function (SMF) 124; a NetworkExposure Function (NEF) 123; a Policy Control Function (PCF) 126; aNetwork Function Repository Function (NRF) 125; a Unified DataManagement (UDM) 127; an application function (AF) 128; a user planefunction (UPF) 102; and a Network Slice Selection Function (NSSF) 129,each with or as respective components for processing corresponding 5GCnetwork functions (NFs) or performance measurements related thereto asnetwork functions associated with any one or more of the embodimentsherein. Tunnelling or persistent transport connections associated withany embodiments can include a stream, connection such as a logicalchannel, logical connection, logical channel, or the like, which can beused for measurement task/activities/jobs associated with the NFs, orrelated measurements, KPIs, or service-based communications for thenetwork. One or more components of the system 100 can be employed orutilized with, in or as a part of a user equipment (UE) (e.g., a mobiledevice, wireless device, or the like), a server provider networkdevice/component (e.g., a network access node, network orchestrator,network server, rack server, network controller/processor, network database, or the like), a computer premise equipment (CPE) (e.g., a router,residential/entity GW, access node, AP, base station, evolved/nextgeneration NodeB (eNB/gNB), or the like).

The UPF 102 can act as an anchor point for intra-RAT and inter-RATmobility, an external protocol data unit (PDU) session point ofinterconnect to DN 103, and a branching point to support multi-homed PDUsession. The UPF 102 can also perform packet routing and forwarding,perform packet inspection, enforce the user plane part of policy rules,lawfully intercept packets (UP collection), perform traffic usagereporting, perform QoS handling for a user plane (e.g., packetfiltering, gating, uplink (UL)/downlink (DL) rate enforcement), performUplink Traffic verification (e.g., Service Data Flow (SDF) to Quality ofService (QoS) flow mapping), transport level packet marking in theuplink and downlink, and perform downlink packet buffering and downlinkdata notification triggering. UPF 102 can include an uplink classifierto support routing traffic flows to a data network. The DN 103 canrepresent various network operator services, Internet access, orthird-party services. DN 103 can include, or be similar to, anapplication server. The UPF 102 can interact with the SMF 124 via an N4reference point between the SMF 124 and the UPF 102.

The AUSF 122 can store data for authentication of UE 101 and handleauthentication-related functionality. The AMF 121 can be responsible forregistration management (e.g., for registering UE 101, etc.), connectionmanagement, reachability management, mobility management, and lawfulinterception of AMF-related events, and access authentication andauthorization. The AMF 121 can be a termination point for the N11reference point between the AMF 121 and the SMF 124. The AMF 121 canprovide transport for session management (SM) messages between the UE101 and the SMF 124, and act as a transparent proxy for routing SMmessages. AMF 121 can also provide transport for SMS messages between UE101 and a Short Message Service (SMS) function (SMSF). AMF 121 can actas Security Anchor Function (SEAF), which can include interaction withthe AUSF 122 and the UE 101, receipt of an intermediate key that wasestablished as a result of the UE 101 authentication process. WhereUniversal Subscriber Identity Module (USIM) based authentication isused, the AMF 121 can retrieve the security material from the AUSF 122.AMF 121 can also include a Security Context Management (SCM) function,which receives a key from the SEAF that it uses to derive access-networkspecific keys. Furthermore, AMF 121 can be a termination point of a RANCP interface or RAN connection point interface, which can include or bean N2 reference point between the (R)AN 210 and the AMF 121; and the AMF121 can be a termination point of Non Access Stratum (NAS) layer (N1)signalling, and perform NAS ciphering and integrity protection.

AMF 121 can also support NAS signalling with a UE 101 over an N3Interworking Function (IWF) interface. The N3 IWF can be used to provideaccess to untrusted entities. N3IWF can be a termination point for theN2 interface between the (R)AN 210 and the AMF 121 for the controlplane, and can be a termination point for the N3 reference point betweenthe (R)AN 210 and the UPF 102 for the user plane. As such, the AMF 121can handle N2 signalling from the SMF 124 and the AMF 121 for PDUsessions and QoS, encapsulate/de-encapsulate packets for IPSec and N3tunnelling, mark N3 user-plane packets in the uplink, and enforce QoScorresponding to N3 packet marking taking into account QoS requirementsassociated with such marking received over N2. N3IWF can also relayuplink and downlink control-plane NAS signalling between the UE 101 andAMF 121 via an N1 reference point between the UE 101 and the AMF 121,and relay uplink and downlink user-plane packets between the UE 101 andUPF 102. The N3IWF also provides mechanisms for IPsec tunnelestablishment with the UE 101. The AMF 121 can exhibit a Namfservice-based interface, and can be a termination point for an N14reference point between two AMFs 121 and an N17 reference point betweenthe AMF 121 and a 5G-Equipment Identity Register (EIR) (not shown byFIG. 1 ).

The UE 101 can register with the AMF 121 in order to receive networkservices. Registration Management (RM) is used to register or deregisterthe UE 101 with the network (e.g., AMF 121), and establish a UE contextin the network (e.g., AMF 121). The UE 101 can operate in anRM-REGISTERED state or an RM-DEREGISTERED state. In the RM-DEREGISTEREDstate, the UE 101 is not registered with the network, and the UE contextin AMF 121 holds no valid location or routing information for the UE 101so the UE 101 is not reachable by the AMF 121. In the RM-REGISTEREDstate, the UE 101 is registered with the network, and the UE context inAMF 121 can hold a valid location or routing information for the UE 101so the UE 101 is reachable by the AMF 121. In the RM-REGISTERED state,the UE 101 can perform mobility Registration Update procedures, performperiodic Registration Update procedures triggered by expiration of theperiodic update timer (e.g., to notify the network that the UE 101 isstill active), and perform a Registration Update procedure to update UEcapability information or to re-negotiate protocol parameters with thenetwork, among others.

Connection Management (CM) can be used to establish and release asignaling connection between the UE 101 and the AMF 121 over the N1interface. The signaling connection is used to enable NAS signalingexchange between the UE 101 and the CN 120, and comprises both thesignaling connection between the UE and the Access Network (AN) (e.g.,Radio Resource Control (RRC) connection or UE-N3IWF connection fornon-3GPP access) and the N2 connection for the UE 101 between the AN(e.g., RAN or memory 230) and the AMF 121.

The SMF 124 can be responsible for SM (e.g., session establishment,modify and release, including tunnel maintain between UPF and AN node);UE IP address allocation and management (including optionalauthorization); selection and control of UP function; configuringtraffic steering at UPF to route traffic to proper destination;termination of interfaces toward policy control functions; controllingpart of policy enforcement and QoS; lawful intercept (for SM events andinterface to LI system); termination of SM parts of NAS messages;downlink data notification; initiating AN specific SM information, sentvia AMF over N2 to AN; and determining SSC mode of a session. SM canrefer to management of a PDU session, and a PDU session or “session” canrefer to a PDU connectivity service that provides or enables theexchange of PDUs between a UE 101 and a data network (DN) 103 identifiedby a Data Network Name (DNN). PDU sessions can be established upon UE101 request, modified upon UE 101 and 5GC 110 request, and released uponUE 101 and 5GC 110 request using NAS SM signaling exchanged over the N1reference point between the UE 101 and the SMF 124. Upon request from anapplication server, the 5GC 110 can trigger a specific application inthe UE 101. In response to receipt of the trigger message, the UE 101can pass the trigger message (or relevant parts/information of thetrigger message) to one or more identified applications in the UE 101.The identified application(s) in the UE 101 can establish a PDU sessionto a specific DNN. The SMF 124 can check whether the UE 101 requests arecompliant with user subscription information associated with the UE 101.In this regard, the SMF 124 can retrieve and/or request to receiveupdate notifications on SMF 124 level subscription data from the UDM127.

The NEF 123 can provide means for securely exposing the services andcapabilities provided by 3GPP network functions for third party,internal exposure/re-exposure, Application Functions (e.g., AF 128),edge computing or fog computing systems, etc. In such embodiments, theNEF 123 can authenticate, authorize, and/or throttle the AFs. NEF 123can also translate information exchanged with the AF 128 and informationexchanged with internal network functions. For example, the NEF 123 cantranslate between an AF-Service-Identifier and an internal 5GCinformation. NEF 123 can also receive information from other networkfunctions (NFs) based on exposed capabilities of other networkfunctions. This information can be stored at the NEF 123 as structureddata, or at a data storage NF using standardized interfaces. The storedinformation can then be re-exposed by the NEF 123 to other NFs and AFs,and/or used for other purposes such as analytics. Additionally, the NEF123 can exhibit a Neff service-based interface.

The NRF 125 can support service discovery functions, receive NFdiscovery requests from NF instances, and provide the information of thediscovered NF instances to the NF instances. NRF 125 also maintainsinformation of available NF instances and their supported services. Asused herein, the terms “instantiate,” “instantiation,” and the like canrefer to the creation of an instance, and an “instance” can refer to aconcrete occurrence of an object, which can occur, for example, duringexecution of program code, wherein a job or measurement instanceincludes a particular task or measurement activity to measure anyparticular parameter, metric, related to a KPI for any of the NFs.Additionally, the NRF 125 can exhibit the Nnrf service-based interface.

The UDM 127 can handle subscription-related information to support thenetwork entities' handling of communication sessions and can storesubscription data of UE 101. For example, subscription data can becommunicated between the UDM 127 and the AMF 121 via an N8 referencepoint between the UDM 127 and the AMF. The UDM 127 can include twoparts, an application FE and a Uniform Data Repository (UDR) (the FE andUDR are not shown by FIG. 2 ). The UDR can store subscription data andpolicy data for the UDM 127 and the PCF 126, and/or structured data forexposure and application data (including PFDs for application detection,application request information for multiple UEs 101) for the NEF 123.

The NSSF 129 can select a set of network slice instances serving the UE101. The NSSF 129 can also determine allowed NSSAI and the mapping tothe subscribed single Network Slice Selection Assistance Information(S-NSSAIs). The NSSF 129 can also determine the AMF set to be used toserve the UE 101, or a list of candidate AMF(s) 121 based on a suitableconfiguration and possibly by querying the NRF 125. The selection of aset of network slice instances for the UE 101 can be triggered by theAMF 121 with which the UE 101 is registered by interacting with the NSSF129, which can lead to a change of AMF 121. The NSSF 129 can interactwith the AMF 121 via an N12 reference point between AMF 121 and NSSF129; and can communicate with another NSSF 129 in a visited network viaan N31 reference point (not shown by FIG. 2 ). Additionally, the NSSF129 can exhibit a Nnssf service-based interface.

Additionally, there can be many more reference points and/orservice-based interfaces between the NF services in the NFs; however,these interfaces and reference points have been omitted from FIG. 1 forclarity. In one example, the CN 120 can include a Nx interface, whichcan be an inter-CN interface between the Mobility Management Entity(MME) and the AMF 121 in order to enable interworking between CN 120 andother CN. Other example interfaces/reference points can include anN5g-Equipment Identity Register (EIR) service-based interface exhibitedby a 5G-EIR, an N27 reference point between the Network RepositoryFunction (NRF) in the visited network and the NRF in the home network;and an N31 reference point between the NSSF in the visited network andthe NSSF in the home network. Further, any of the above functions,entities, etc. can be considered or include a component as referred toherein.

Referring to FIG. 2 , illustrated is a block diagram of a system 200employable at a UE (e.g., UE 101), a next generation Node B (gNB, or AN110) or other BS (base station)/TRP (Transmit/Receive Point), or acomponent of a 3GPP (Third Generation Partnership Project) network(e.g., a 5GC (Fifth Generation Core Network)) component such as a UPF(User Plane Function)) that facilitates generation and/or communicationof performance measurements associated with one or more of a PDU(Protocol Data Unit) session and/or a N4 session, in embodiments. System200 can include processor(s) 210 comprising processing circuitry andassociated interface(s) (e.g., a communication interface forcommunicating with communication circuitry 220, a memory interface forcommunicating with memory 230, etc.), communication circuitry 220 (e.g.,comprising circuitry for wired and/or wireless connection(s), e.g.,transmitter circuitry (e.g., associated with one or more transmitchains) and/or receiver circuitry (e.g., associated with one or morereceive chains), wherein transmitter circuitry and receiver circuitrycan employ common and/or distinct circuit elements, or a combinationthereof), and a memory 230 (which can comprise any of a variety ofstorage mediums and can store instructions and/or data associated withone or more of processor(s) 210 or the communication circuitry 220 astransceiver circuitry). Specific types of embodiments (e.g., UEembodiments) can be indicated via subscripts (e.g., system 200comprising processor(s) 210 (e.g., of a UE), communication circuitry220, and memory 230). In BS embodiments (e.g., system 200 of a gNB) andnetwork component (e.g., UPF (User Plane Function), etc.) embodiments(e.g., system 200 of a UPF) processor(s) 210 of the gNB (etc.),communication circuitry 220 (etc.), and memory 230 (etc.) can be in asingle device or can be included in different devices, such as part of adistributed architecture. In embodiments, signaling or messaging betweendifferent embodiments of system 200 can be generated by processor(s)210, transmitted by communication circuitry 220 over a suitableinterface or reference point (e.g., N4, etc.), received by communicationcircuitry 220, and processed by processor(s) 210.

Referring to FIG. 3 , illustrates an example network slicing system 300for a Network Slice as a Service (NSaaS) with various components. Thenetwork slice system 300, for example, can include a communicationservice customer (CSC) 302, a communication service provider (CSP) 304,a network operator (NOP) 306, a network slice customer (NSC) 308, anetwork slice provider (NSP) 310, or other component(s) not illustratedfor facilitating network slicing or network slice instances as describedherein to an end-user device or UE 101. Services such as communicationservices, networking services, application services or the like, can bereferred to herein to include a data streaming service, an online gamingservice, telecommunication services, or other services communicated viaa network interface, either wired or wireless. These services, forexample, can be a part of NSaaS.

The CSC 302 can be configured to utilize communication services as, forexample, a UE device 101, an end-user device, a tenant or a vertical.The CSC 302 can be provided service or a network slice by the CSC 304 asa client or further provide networking service or use of the networkslice to the NSC 308.

The CSP 304 can be configured to provide communication services andbuilds/establishes its own communication services, in which it cangovern or control. The CSP 304 can provide the communication servicewith or without a network slice, which can be a separate network thatoperates on physical hardware for different applications, services, orpurposes by separating the control plane from user plane function. Eachnetwork slice can have its own architecture provisional management andsecurity that supports one or more specific use cases. Functions such asspeed, capacity, connectivity, and coverage can be allocated via thenetwork slice to meet any requirements of a particular objection orprimary purpose, for example. The CSP 304 can be a provider of a serviceby providing a network slice or a service to the CSC 302, NSC 308, orNSP 310, for example, in which as a provider can control the managementand use of the network slice or service to an customer component such asan end-user, UE or other component device. The CSP 304 can also be aclient to receive such management or control of network slicing from theNOP 306, for example, or other component of a CN 120, or the like.

The NOP 306 can provide a network slice or service to the CSC 302, theNSP 304, or the NSP 310, for example, as a provider. The NOP 306 can beconfigured to design, build, and operate its networks to offer relatedservices to one or more clients, either directly or indirectly viacommunication interfacing. The NOP 306 can operate as a component of orbe communicatively coupled to the CN 120 or a central entity, forexample.

The NSC 308 can operate to obtain use of a network slice as a NSaaS byanother component/device so that services can be utilized such as anapplication relying upon the service for operation (e.g., gaming, datastreaming, augmented reality, or the like). For example, the NSC 308 canbe configured as a client, an end-user device or UE, for example, thatuses the network slice according to an assigned service.

The NSP 310 can further provide services or a network slice obtainedfrom another component to the NSC 308. The NSP 310 can operate as aprovider by further designing, building, operating, controlling, ormanaging a network slice or service in response to obtaining or beingassigned the network slice or service. The NSP 310 can also be orcomprise the NOP 306 to provide network slicing as a NSaaS.

NSaaS or Network Slice as a Service as defined in section 4.1.6 in 3GPPTS 28.530, and referred to herein, can be offered by the CSP 304 to itsCSC 302 in the form of a service (e.g., gaming, augmented reality, datastreaming, or the like). This service allows the CSC 302 to use thenetwork slice instance as the end user or optionally allows the CSC 302to manage the network slice instance as manager via a managementinterface exposed by the CSP 304, for example. In turn, the CSC 302 canplay the role of the CSP 304 and offer their own services (e.g.communication services) on top of the network slice instance obtainedfrom the CSP 304. For example, a network slice customer or NSC 308 canalso play the role of NOP 306 and could build their own networkcontaining the network slice obtained from the CSP 304 as a “buildingblock”. In this model, both CSP 304 offering NSaaS and CSC 302 consumingNSaaS have the knowledge of the existence of network slice instances.Depending on the service offering, the CSP 304 offering NSaaS can imposelimits on the NSaaS management capabilities exposure to the CSC 302, andthe CSC 302 can manage the network slice instance according to NSaaSmanagement capabilities exposed and agreed upon limited level ofmanagement by the CSP 304. Likewise, the NSP 310 can operate as aprovider CSP 304 for the client NSC 308, or the CSC 302/NSC 308 canoperate as a provider of the network slice to an end-user or UE device,for example.

FIG. 4 is an example of diagram of a communication flow 400 for a UERoute Selection Policy (URSP) to enable network slicing. The processflow components comprise a UE 401 (e.g., UE 101), a RAN 410 (e.g., (R)AN110), an AMF 421 (e.g., AMF 121), and PCF 426 (e.g., PCF 126). The AMF421 and the PCF 426 can operate as an NSP for network slicing as an NOP,a central network entity, or core network for example, and the RAN canoperate as an NSC providing services on the network slice to the UE 402or end-user, for example.

A URSP can be used by the UE 401 to determine if a detected application(e.g., online gaming application, augmented reality application, datastreaming application, or the like) can be associated to an establishedPDU Session, can be offloaded to non-3GPP access outside a PDU session,or can trigger the establishment of a new PDU Session. As such, the PDUsession can operate as a logical connection between a UE 401 and a datanetwork or network slice. A URSP can be pre-configured in the UE 402 orcan be provisioned to UE 401 from the PCF 426 using a transparentcontainer included in a NAS transport message, such as signals 411 thru414. The signal message 411 comprises a PCF request delivery of a URSPpolicy, signal message 412 comprises a downlink (DL) NAS transport in aUE policy container from the AMF 421 to the RAN 410, and the signalmessage 414 is a radio resource control message with the message 412. Inresponse to receiving the UE policy, the UE 401 can then provide themessage 416 comprising an RRC message UL NAS transport UE policycontainer. The RAN 410 receives the message 416 and provides an uplinkmessage 418 as a UL NAS Transport UE policy container policy RSPmessage.

A URSP rule includes one traffic descriptor that specifies the matchingcriteria and one or more of the route selection descriptors, whichdefine the parameters of the PDU session to be used to transfer thetraffic data. The traffic descriptor contains one or more of thefollowing components: application identifiers, IP 3 tuples, non-IPdescriptors, data network names (DNNs), connection capabilities anddomain descriptors, i.e. destination fully qualified domain name(s)(FQDN(s)). According to embodiments or aspects herein, the trafficdescriptor can include an NSC Service ID. A route selection descriptorcan contain multiple elements (e.g., a PDU session type, a session andservice continuity (SSC) mode, S-NSSAIs or DNNs.

The URSP can be evaluated by the UE 401 as is referenced in 3GPP TS23.503, for example. For every newly detected application the UE 401 canevaluate the URSP rules in an order of rule precedence and determine ifthe application is matching the traffic descriptor of a URSP rule. Whena URSP rule is determined to be applicable for a given application (seeclause 6.6.2.1), the UE 401 can select a route selection descriptorwithin this URSP rule in the order of a route selection descriptorprecedence. When a valid route selection descriptor is found, the UE 401determines if there is an existing PDU Session that matches allcomponents in the selected route selection descriptor. When a matchingPDU Session exists, the UE 401 associates the application to theexisting PDU Session by routing the traffic of the detected applicationon this PDU Session. If none of the existing PDU Sessions matches, theUE 101 can try to establish a new PDU Session using the values specifiedby the selected route selection descriptor.

The following is an example of URSP rule as clarified in Annex A in 3GPPTS 23.503:

Example URSP rules Comments Rule Route Selection This URSP ruleassociates the traffic Precedence = 3 Descriptor of applications thatare configured to Traffic Precedence = 1 use DNN_1 with DNN_1, S-NSSAI-aDescriptor: Network Slice Selection: over Non-3GPP access. DNN = DNN_1S-NSSAI-a It enforces the following routing Access Type preference:policy: Non-3GPP access The traffic of application(s) that areconfigured to use DNN_1 should be transferred on a PDU sessionsupporting S-NSSAI-a over Non- 3GPP access. If this PDU session is notestablished, the UE shall attempt to establish the PDU session with S-NSSAI-a over Non-3GPP access.

Various concerns can be addressed according to aspects/embodimentsherein. The application ID of an end user device or UE 101 (401)application is not shared with the network or the NSP, central operatoror central core network entity in order to avoid impacting or preservinguser privacy of the UE 101. A non-IP descriptor can be only used forapplications transferred in a non-IP type PDU session. IP 3 tuples orthe IP address of the application server is not necessarily unique andcould be changed dynamically in a short time. A DNN is not mandatorythat all application(s) in one DNN must use a same network slice.Consequently, a new or additional traffic descriptor element/component,referred to herein as an NSC Service ID can be configured to enable anetwork component to link an application to a correct slice withoutimpacting user privacy of the UE or end user in particular.

FIG. 5 illustrates an example of an NSC Service ID 500 in accord withvarious aspects herein. The NSC Service ID 502 container can beconfigured to include an NSC Unique ID 504 and a Service ID 506. The NSCUnique ID 504 can be unique to the particular NSC and identifies the NSCoffering a particular application service from among one or morecommunication services on a network slice or network slice instance (asa particular set of network resources or dedicated network resources).In Network Slice as a Service (NSaaS), a network component (e.g.,Network Operator 306, core network 120 component (e.g., UPF 102, AMF121, PCF 126, etc.), or an NSP 310 can provide a network slice based ona request from NSC 308 or (R)AN 110. The NSC 308 (e.g., (R)AN 110) canprovide a communication service based on the provided network slice andenable end users or the UE 101 to use the provided network slice.Communication services can comprise any number of services on a networkslice including, but not limited to, gaming operations,telecommunications, data streaming (e.g., video, chat, virtual reality,music, etc.), augmented reality (AR), or the like, which can be furtherassociated to a particular application or application service at the UEby an application ID (app ID), for example.

The NSC Unique ID 504 can be obtained by the NSC, for example, from aglobal entity (e.g., 3GPP, a global system for mobile communicationsalliance (GSMA). This can be independent of a network slice provider(NSP 310), a network operator 306, or a core network 120 component.Alternatively, or additionally, the NSC 308 can obtain the NSC ServiceID after negotiation with operator. At least a portion (e.g., the NSCUnique ID 504, the NSC Service ID 506, or the NSC Service ID 502container) of the NSC Service ID 500 can be unique per operator ormanager of the network slice. In this case, when the UE 101 or userdevice switches or changes the universal mobile telecommunication system(UMTS) subscriber identity module (USIM), a repeat of theregistration/binding of the application to the specific NSC Service ID502 of the NSC 308 can be performed. In one example, the NSC Unique ID504 can be at least 16 bits.

The Service ID 506 can be assigned to a particular communication serviceor application service for an application to use the network slice. Forexample, the Service ID can designate that only online gamingoperations/services. Other services or application operations can alsobe assigned to the Service ID and not are not necessarily limited to theexample of online gaming. In an aspect, a single application service(e.g., online gaming, or other service) can be designated or assigned tothe Service ID 506 so that one or a multiple of UEs/user devices canutilize the network slice according to the particular application ID ofan application (e.g., game or other data application) for use of theparticular service with the network slice obtained by the NSC 308. TheService ID can be assigned, negotiated or designated by the NSC 308 withthe NSP 310 (as a network operator, or CN component) for associationwith the network slice, which can be reserved as dedicated resources(e.g., storage amount, bandwidth, processing power, attribute names andtheir definitions for a supported throughput in uplink or downlink, adelay, a coverage area of the slice, etc.) as isolated from othernetwork slices, for example.

The UE 101, for example, can further receive the NSC Service ID 502 fromthe NSC and a URSP from a network operator as an NSP with the NSCService ID as a traffic descriptor. The traffic descriptor can furthercomprise a rule for associating the NSC Service ID with an S-NSSAI toenable use of the correct network slice for the particular communicationservice for an application at the UE 101. The UE 101 thus does not haveto share the App ID of the application with the NSP.

FIG. 6 illustrates an example network system 600 for a network slice ofNSaaS in accord with various aspects being described herein. The system600 includes an NSC 602, a UE 604 and an NSP 606. The UE 604 can beconfigured as UE 101, 200, 401 or any end user device as describedherein. The NSC 602 can be configured as the NSC 308, and the NSP 606can be configured as the NSP 310 as a network operator 306, or anothercore network 120 component.

The NSP 606 can be configured to generate a URSP comprising a rule thatlinks the NSC Service ID 500 (502) with an S-NSSAI of a network slice.This can be done in response to a communication from the NSC 602requesting the network slice, or an assignment of an NSC Unique ID 502or the NSC Service ID 502 to the NSC 602 for the network slice. This canbe done without any communication by the UE 604 with the NSP 606, forexample. In response to a request by the NSC 602 to the NSP 606 for anetwork slice, the NSP 606 can provide a network slice type (NEST) withthe NSC Service ID 502 comprising the NSC Unique ID 504 and the ServiceID 506. The NEST can define characteristics of the network slicedassigned to the NSC 602. Such characteristics can include attributenames, and their definitions for a supported throughput in uplink ordownlink, a delay, a coverage area of the slice, or other dedicatedresources, for example.

The NSP 606 can be configured to modify the URSP to comprise the NSCServer ID 502 or at least a portion thereof (e.g., NSC Unique ID 502,Service ID 504) as a valid traffic descriptor. The NSP 606 as anoperator can be configured to add a rule in the URSP to link the NSCService ID 502 to the S-NSSAI for linking traffic to the network sliceassigned to the NSC 602. The following is an example of the URSP rulegenerated by the NSP 606 as an operator and provided to the UE 604 forassociation of the NSC Service ID to a network slice obtained by the NSC602:

Example URSP rules Comments Rule Route Selection This URSP ruleassociates the Precedence = 1 Descriptor traffic of application relatedto NSC Traffic Precedence = 1 Service ID 1 with S-NSSAI-a, SSCDescriptor: Network Slice Selection: Mode 3, 3GPP access and the NSCS-NSSAI-a “internet” DNN. Identifiers = SSC Mode Selection: It enforcesthe following routing policy: NSC Service ID SSC Mode 3 The traffic ofapplication related to 1 DNN Selection: internet NSC Service ID 1 shouldbe Access Type preference: transferred on a PDU session 3GPP accesssupporting S-NSSAI-a, SSC Mode 3 and DNN = internet over 3GPP access. Ifthis PDU session is not established, the UE shall attempt to establish aPDU session with S-NSSAI-a, SSC Mode 3 and the “internet” DNN over 3GPPaccess.

As state above, the URSP includes a traffic descriptor comprising theNSC Service ID and a rule that associates the NSC Service ID with anS-NSSAI that enables the UE 604 to route traffic to the network sliceassigned to the NSC 602 in NSaaS based on the NSC Service ID and theS-NSSAI. The URSP rule in the URSP is provided to the UE 604 by the NSP606, while the NSC Service ID is provided to the UE 604 by the NSC 602.The URSP rule is configured to associate traffic of the application tothe NSC Service ID with the S-NSSAI, and can further comprise at leastone of: a session and service continuity (SSC) mode, a preferred accesstype, or a data network name (DNN). In the present example, the DNN canindicate “internet”.

The UE 604 can determine whether the NSC Service ID from the NSC 602 isassociated with an online gaming service based on a service ID of theNSC Service ID. The UE can further determine whether an application IDassociated with an application or application service (e.g., an onlinegaming service, or other service) matches the URSP rule of the URSP inresponse to an initiation of the application or application service.Then the UE 604 can further determine whether an existing packet dataunit session or PDU session matches a route selection descriptor of atraffic descriptor that comprises the NSC Service ID and the S-NSSAI,linking the two for a particular network slice identified by the NSC602. In response to a determination that the NSC Service ID isassociated with the service, a match of the application ID with the URSPrule of the URSP, and the existing PDU session matching the routeselection descriptor, the UE can associate the application service(e.g., an online gaming service, data streaming, or other applicationservice) to the existing PDU session on the network slice that isassociated with the S-NSSAI.

FIG. 7 illustrates an example data flow 700 in accord with variousaspects herein. An NSC 704, for example, can communicate a request for anetwork slice instance and obtain an NSC Service ID 500 for the networkslice from a network component 706, an operator, an NSP or anotherprovider component. The UE 702 is provided with the NSC service ID 712from the NSC 704, and the NW 706 links the NSC Service ID to the S-NSSAIfor connecting the network slice at 714. At 716, a registrationprocedure can be processed or a configuration update procedure can bepreformed to provide the UE 702 newly active S-NSSAI as configured at714, which includes the S-NSSAI for the NSC service orcommunication/application service to be provided on the network slice.The NW 716 provides the UE 702 in a downlink NAS transport message a UEpolicy container to provide the UE with a URSP rule that links the NSCservice ID to the S-NSSAI. At 720, when the UE 702 desires to initiatethe application related to the NSC service, the UE 702 follows the URSP;based on the rule that links the NSC service with the S-NSSAI, the UE702 can link a PDU session with the correct S-NSSAI for the correctnetwork slice. At 722, a PDU session establishment procedure can beperformed using the S-NSSAI linked to the NSC service.

Referring to FIG. 8 , illustrated is an example process flow 800 for anetwork device or component (e.g., UE 101, base station 110, AN 110 orother network component) to enable network slicing based on an NSCService ID of an NSC and a URSP of an NSP, network operator or CNcomponent.

The process flow initiates at 802 with receiving, from an NSP, a UEroute selection policy (URSP) comprising a traffic descriptor thatincludes an NSC Service ID. At 804, the process flow 800 furthercomprises determining an application service derived from the NSCService ID. At 806, the process flow 800 further comprises determining asingle network slice selection assistance information (S-NSSAI) from theURSP. At 808, the process flow 800 comprises linking the applicationservice to a network slice based on the NSC Service ID and the S-NSSAI.

The process flow 800 can further comprise receiving the NSC Service IDfrom a network slice customer (NSC) that identifies the applicationservice and the NSC providing the application service to the UE with thenetwork slice. In response to detecting initiation of an application ofthe application service, the process flow can include routing traffic tothe network slice based on the NSC Service ID associated with theS-NSSAI without sharing an application identifier of the applicationwith the NSP. An NSC unique ID can be determined from the NSC ServiceID, and the application service assigned to the network slice can bedetermined from a service ID of the NSC Service ID, in which the NSCService ID enables an association of the NSC with the applicationservice for the network slice.

The process flow 800 can further comprise determining whether the NSCService ID is associated with an online gaming service based on aservice ID of the NSC Service ID; determining whether an application IDassociated with the online gaming service matches a URSP rule of theURSP in response to an initiation of the online gaming service;determining whether an existing packet data unit (PDU) session matches aroute selection descriptor of a traffic descriptor that comprises theNSC Service ID and the S-NSSAI; and in response to a determination thatthe NSC Service ID is associated with the online gaming service, a matchof the application ID with the URSP rule of the URSP, and the existingPDU session matching the route selection descriptor, associating theonline gaming service to the existing PDU session on the network slicethat is associated with the S-NSSAI.

Referring to FIG. 9 , illustrated is an example process flow 900 for anetwork device or component (e.g., UE 101, base station 110, AN 110, NSC308, 602 or other network component) to enable network slicing based onan NSC Service ID of an NSC and a URSP of an NSP, network operator or CNcomponent as NW 706.

The process flow 900 initiates at 902 with providing a request to obtaina network slice of a network slice as a service (NSaaS) to provide acommunication service on the network slice for an end-user device. At904, the process flow 900 includes determine a network slice customer(NSC) Service identity (ID) associated with the network slice inresponse to obtaining the network slice. At 906, the process flow 900includes providing the NSC Service ID for the communication service tobe performed on the network slice by the end-user device.

The process flow 900 can further include receiving the NSC Service IDfrom a network slice provider (NSP), a network operator or a corenetwork component to assign the access node as a network slice customer(NSC) for the network slice. The Network Service ID comprises a uniqueID (NSC Unique ID) that is independent of a network operator or otherNSCs. The NSC unique ID can be obtained within the NSC Service ID from aglobal entity that comprises at least one of: a global system for mobilecommunications alliance (GSMA) or 3GPP independent of a network sliceprovider (NSP), a network operator or a core network component. The NSCService ID can enable a UE or end-user device to utilize the obtainednetwork slice and for a single application service as the communicationservice to be associated to the NSC Service ID based on a URSP thatincludes the NSC Service ID in a traffic descriptor.

Referring to FIG. 10 , illustrated is an example process flow 1000 for anetwork device or component (e.g., UE 101, base station 110, AN 110, NSC308, 602 or other network component such as NSP 310, 606) to enablenetwork slicing based on an NSC Service ID of an NSC and a URSP of anNSP, network operator or CN component as NW 706.

The process flow 1000 initiates at 1002 with communicatively coupling toa network slice customer (NSC). At 1004, the process flow 1000 includesreceiving a request from the NSC to obtain or reserve a network slice ofthe NSaaS. At 1006, the process flow 1000 includes assigning a networkslice to the NSC in response to the request by the NSC. At 1008, theprocess flow 1000 includes providing a user equipment (UE) routeselection policy (URSP) comprising a traffic descriptor that includes anNSC Service ID.

The process flow 1000 can further include generating a URSP rule of theURSP that associates traffic of an application to the NSC Service IDwith an S-NSSAI, and further comprises at least one of: a session andservice continuity (SSC) mode, a preferred access type, or a datanetwork name (DNN). The NSC Service ID comprises an NSC unique IDassociated with the NSC and a service ID associated with a communicationservice to be provided by the NSC on the network slice. A downlink (DL)non-access stratum (NAS) transport UE policy container message can beprovided with a rule of the URSP that links the NSC Service ID to theS-NSSAI to enable an association of a packet data unit (PDU) sessionwith the S-NSSAI for an application of a communication service on thenetwork slice. The NSC Unique ID can be provided to the NSC todistinguish the NSC among other NSCs providing a communication serviceand provide a Service ID for the NSC to associate the communicationservice on the network slice.

As it is employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or deviceincluding, but not limited to including, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit, a digital signalprocessor, a field programmable gate array, a programmable logiccontroller, a complex programmable logic device, a discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions and/or processes describedherein. Processors can exploit nano-scale architectures such as, but notlimited to, molecular and quantum-dot based transistors, switches andgates, in order to optimize space usage or enhance performance of mobiledevices. A processor can also be implemented as a combination ofcomputing processing units.

Examples (embodiments) can include subject matter such as a method,means for performing acts or blocks of the method, at least onemachine-readable medium including instructions that, when performed by amachine (e.g., a processor with memory, an application-specificintegrated circuit (ASIC), a field programmable gate array (FPGA), orthe like) cause the machine to perform acts of the method or of anapparatus or system for concurrent communication using multiplecommunication technologies according to embodiments and examplesdescribed herein.

A first example is an apparatus configured to be employed in a userequipment (UE) for a new radio (NR) network comprising: one or moreprocessors configured to: receive, from a network slice customer (NSC),an NSC Service ID that associates the NSC with a communication service;receive, from a network slice provider (NSP), a UE route selectionpolicy (URSP) comprising a traffic descriptor comprising the NSC ServiceID and a rule that associates the NSC Service ID with a single networkslice selection assistance information (S-NSSAI); and in response todetecting an execution of an application of the communication service,route data traffic to a network slice instance of a network slice as aservice (NSaaS) based on the NSC Service ID from the NSC and the S-NSSAIassociated with the NSC Service ID according to the URSP from the NSP.

A second example can include the first example, wherein the one or moreprocessors are further configured to: associate the NSC Service ID to asingle application of the communication service based on a service ID ofthe NSC Service ID.

A third example can include the first or second example, wherein therule of the URSP indicates that the NSC Service ID is associated withthe network slice instance of the NSaaS based on the S-NSSAI.

A fourth example can include any one or more of the first through thirdexamples, wherein the one or more processors are further configured to:establish a routing session for a gaming service as the communicationservice based on an application ID of the gaming service associated withthe NSC Service ID without sharing the application ID to the NSP.

A fifth example can include any one or more of the first through fourthexamples, wherein the NSC Service ID comprises an NSC unique IDassociated with the NSC and a service ID associated with thecommunication service provided by the NSC.

A sixth example can include any one or more of the first through fifthexamples, wherein the communication service comprises online gamingservices.

A seventh example can include any one or more of the first through sixthexamples, wherein the NSC unique ID identifies the NSC from amongdifferent NSCs.

An eighth example can include any one or more of the first throughseventh examples, wherein the one or more processors are furtherconfigured to receive a downlink (DL) non-access stratum (NAS) transportUE policy container message to receive the rule of the URSP that linksthe NSC Service ID to the S-NSSAI to enable an association of a packetdata unit (PDU) session with the S-NSSAI for the application of thecommunication service on the NSaaS.

A ninth example can include any one or more of the first through eighthexamples, wherein the rule of the URSP associates traffic of theapplication to the NSC Service ID with the S-NSSAI, and furthercomprises at least one of: a session and service continuity (SSC) mode,a preferred access type, or a data network name (DNN), for example“internet”.

A tenth example can include any one or more of the first through ninthexamples, wherein the one or more processors are further configured torelease, suspend, or resume the data traffic on the network sliceinstance only by the NSC Service ID received from the NSC and theS-NSSAI in the traffic descriptor of the URSP received from the NSP,wherein the NSP comprises a network operator that assigns the NSCService ID to the NSC for the network slice instance.

An eleventh example can include any one or more of the first throughtenth examples, wherein the network slice instance is associated with anapplication service consisting of only online gaming that is indicatedin the NSC Service ID received from the NSC.

An twelfth example can include any one or more of the first througheleventh examples, wherein the one or more processors are furtherconfigured to repeat a registration or a binding of an application toanother NSC Service ID in response to changing a universal mobiletelecommunication system (UMTS) subscriber identity module (USIM).

A thirteenth example is a tangible computer readable storage devicestoring executable instructions that, in response to execution, causeone or more processors of a user equipment (UE) to perform operations,the operations comprising: receiving, from a network slice provider(NSP), a UE route selection policy (URSP) comprising a trafficdescriptor that includes a network slice customer (NSC) Service ID;determining an application service derived from the NSC Service ID;determining a single network slice selection assistance information(S-NSSAI) from the URSP; and linking the application service to anetwork slice based on the NSC Service ID and the S-NSSAI.

A fourteenth example can include the thirteenth example, the operationsfurther comprising: receiving the NSC Service ID from a network slicecustomer (NSC) that identifies the application service and the NSCproviding the application service to the UE with the network slice.

A fifteenth example can include any one or more of the thirteenththrough the fourteenth examples, the operations further comprising: inresponse to detecting initiation of an application of the applicationservice, routing traffic to the network slice based on the NSC ServiceID associated with the S-NSSAI without sharing an application identifierof the application with the NSP.

A sixteenth example can include any one or more of the thirteenththrough the fifteenth examples, the operations further comprising:determining from the NSC Service ID an NSC unique ID; and determiningthe application service from a service ID of the NSC Service ID, whereinthe NSC Service ID enables an association of the NSC with theapplication service for the network slice.

A seventeenth example can include any one or more of the thirteenththrough the sixteenth examples, the operations further comprising:determining whether the NSC Service ID is associated with an onlinegaming service based on a service ID of the NSC Service ID; determiningwhether an application ID associated with the online gaming servicematches a URSP rule of the URSP in response to an initiation of theonline gaming service; determining whether an existing packet data unit(PDU) session matches a route selection descriptor of a trafficdescriptor that comprises the NSC Service ID and the S-NSSAI; inresponse to a determination that the NSC Service ID is associated withthe online gaming service, a match of the application ID with the URSPrule of the URSP, and the existing PDU session matching the routeselection descriptor, associating the online gaming service to theexisting PDU session on the network slice that is associated with theS-NSSAI.

An eighteenth example can be an apparatus configured to be employed in auser equipment (UE) comprising: one or more processors configured to:receive, from a network slice provider (NSP), a UE route selectionpolicy (URSP) that associates a network slice customer (NSC) Service IDto a traffic descriptor; determine a single network slice selectionassistance information (S-NSSAI) from the URSP; and associate anapplication service to a network slice based on the NSC Service ID andthe S-NSSAI to operate an application that includes the applicationservice on the network slice.

A nineteenth example can include the eighteenth example, wherein the oneor more processors are further configured to determine the applicationservice derived from an NSC service ID in the NSC Service ID from an NSCentity that obtained management of the network slice from the NSP as anetwork operator.

A twentieth example can include any one or more of the eighteenththrough nineteenth examples, wherein the URSP comprises a URSP rule thatassociates the NSC Service ID of the NSC with the S-NSSAI.

A twenty-first example can be an apparatus configured to be employed inan access node for network slicing comprising: one or more processorsconfigured to: provide a request to obtain a network slice of a networkslice as a service (NSaaS) to provide a communication service on thenetwork slice for an end-user device; determine a network slice customer(NSC) Service identity (ID) associated with the network slice inresponse to obtaining the network slice; and provide the NSC Service IDfor the communication service to be performed on the network slice bythe end-user device.

A twenty-second example can include the twenty-first example, whereinthe one or more processors are further configured to receive the NSCService ID from a network slice provider (NSP), a network operator or acore network component to assign the access node as a network slicecustomer (NSC) for the network slice.

A twenty-third example can include any one of the twenty-first throughtwenty-second examples, wherein the Network Service ID comprises aunique ID that is independent of a network operator.

A twenty-fourth example can include any one of the twenty-first throughtwenty-third examples, wherein the one or more processors are furtherconfigured to obtain an NSC unique ID within the NSC Service ID from aglobal entity that comprises at least one of: a global system for mobilecommunications alliance (GSMA) or 3GPP independent of a network sliceprovider (NSP), a network operator or a core network component.

A twenty-fifth example can include any one of the twenty-first throughtwenty-fourth examples, wherein the one or more processors are furtherconfigured to enable a user equipment or the end-user device to utilizethe network slice based on the NSC Service ID.

A twenty-sixth example can include any one of the twenty-first throughtwenty-fifth examples, wherein the one or more processors are furtherconfigured to associate a single application service as thecommunication service to the NSC Service ID.

A twenty-seventh example can include any one of the twenty-first throughtwenty-sixth examples, wherein the one or more processors are furtherconfigured to provide the NSC Service ID to the end-user device with anindication of the single application service that enables the end-userdevice to operate the single application service on the network slicebased on the NSC Service ID and a user equipment (UE) route selectionpolicy (URSP) that comprises a traffic descriptor comprising the NSCService ID and a rule that associates the NSC Service ID with a singlenetwork slice selection assistance information (S-NSSAI).

A twenty-eighth example can include any one of the twenty-first throughtwenty-seventh examples, wherein the one or more processors are furtherconfigured to provide the NSC Service ID comprising a service ID and anNSC unique ID.

A twenty-ninth example can include any one of the twenty-first throughtwenty-eighth examples, wherein the service ID indicates an applicationservice as the communication service to be used on the network slice,wherein the application service comprises at least one of: a datastreaming service, an online gaming service, or an augmented realityservice.

A thirtieth example can include any one of the twenty-first throughtwenty-ninth examples, wherein the one or more processors arecommunicatively coupled to a network slice provider (NSP), a networkoperator or a core network component configured to indicate a rule in aUE route selection policy (URSP) that indicates the NSC Service ID isassociated with the network slice based on an S-NSSAI and enable anassociation of a packet data unit (PDU) session with the S-NSSAI for anapplication service of the communication service on the network slice.

A thirty-first example can include any one of the twenty-first throughthirtieth examples wherein the URSP comprise a traffic descriptor thatincludes the NSC Service ID.

A thirty-second example can be an apparatus configured to be employed inan access node for a network slice as a service (NSaaS) networkcomprising: one or more processors configured to: communicatively coupleto a network slice customer (NSC); receive a request from the NSC toobtain or reserve a network slice of the NSaaS; assign a network sliceto the NSC in response to the request by the NSC; and provide a userequipment (UE) route selection policy (URSP) comprising a trafficdescriptor that includes an NSC Service ID.

A thirty-third example can include the thirtieth example, wherein theone or more processors are further configured to generate a URSP rule ofthe URSP that associates traffic of an application to the NSC Service IDwith an S-NSSAI, and further comprises at least one of: a session andservice continuity (SSC) mode, a preferred access type, or a datanetwork name (DNN), for example “internet”.

A thirty-fourth example can include any one of the thirtieth throughthirty-third examples, wherein the NSC Service ID comprises an NSCunique ID associated with the NSC and a service ID associated with acommunication service to be provided by the NSC on the network slice.

A thirty-fifth example can include any one of the thirtieth throughthirty-fourth examples, wherein the one or more processors are furtherconfigured to provide a downlink (DL) non-access stratum (NAS) transportUE policy container message with a rule of the URSP that links the NSCService ID to the S-NSSAI to enable an association of a packet data unit(PDU) session with the S-NSSAI for an application of a communicationservice on the network slice.

A thirty-sixth example can include any one of the thirtieth throughthirty-sixth examples, wherein the one or more processors are furtherconfigured to provide an NSC Unique ID to the NSC to distinguish the NSCamong other NSCs providing a communication service and provide a ServiceID for the NSC to associate the communication service on the networkslice.

A thirty-seventh example can be a tangible computer readable storagedevice storing executable instructions that, in response to execution,cause one or more processors of an Access Node (AN) to performoperations, the operations comprising: determining a network slicecustomer (NSC) Service identity (ID) associated with a network slice;and providing the NSC Service ID for a communication service to beperformed on the network slice by a user equipment (UE).

A thirty-eighth example can include the thirty-seventh example, theoperations further comprising: provide the NSC Service ID to the UE withan indication of the single application service that enables the UE tooperate the single application service on the network slice based on theNSC Service ID and a UE route selection policy (URSP) that comprises atraffic descriptor comprising the NSC Service ID and a rule thatassociates the NSC Service ID with a single network slice selectionassistance information (5-NSSAI).

A thirty-nineth example can include any one of the thirty-sevenththrough thirty-eighth examples, the operations further comprising:enabling the UE to perform the communication service for an applicationon the network slice based on the NSC Service ID and an S-NSSAI withoutproviding an application ID or without communicating a request to obtainthe network slice for the application.

A fortieth example can include any one of the thirty-seventh throughthirty-nineth examples, the operations further comprising: associating aService ID of the NSC Service ID to a particular communication servicefor an application of the UE that utilizes the communication service andan NSC Unique ID of the NSC service ID with an NSC that obtained thenetwork slice.

Moreover, various aspects or features described herein can beimplemented as a method, apparatus, or article of manufacture usingstandard programming and/or engineering techniques. The term “article ofmanufacture” as used herein is intended to encompass a computer programaccessible from any computer-readable device, carrier, or media. Forexample, computer-readable media can include but are not limited tomagnetic storage devices (e.g., hard disk, floppy disk, magnetic strips,etc.), optical disks (e.g., compact disk (CD), digital versatile disk(DVD), etc.), smart cards, and flash memory devices (e.g., EPROM, card,stick, key drive, etc.). Additionally, various storage media describedherein can represent one or more devices and/or other machine-readablemedia for storing information. The term “machine-readable medium” caninclude, without being limited to, wireless channels and various othermedia capable of storing, containing, and/or carrying instruction(s)and/or data. Additionally, a computer program product can include acomputer readable medium having one or more instructions or codesoperable to cause a computer to perform functions described herein.

Communications media embody computer-readable instructions, datastructures, program modules or other structured or unstructured data ina data signal such as a modulated data signal, e.g., a carrier wave orother transport mechanism, and includes any information delivery ortransport media. The term “modulated data signal” or signals refers to asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in one or more signals. By way ofexample, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

An exemplary storage medium can be coupled to processor, such thatprocessor can read information from, and write information to, storagemedium. In the alternative, storage medium can be integral to processor.Further, in some aspects, processor and storage medium can reside in anASIC. Additionally, ASIC can reside in a user terminal. In thealternative, processor and storage medium can reside as discretecomponents in a user terminal. Additionally, in some aspects, theprocesses and/or actions of a method or algorithm can reside as one orany combination or set of codes and/or instructions on amachine-readable medium and/or computer readable medium, which can beincorporated into a computer program product.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding Figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

In particular regard to the various functions performed by the abovedescribed components (assemblies, devices, circuits, systems, etc.), theterms (including a reference to a “means”) used to describe suchcomponents are intended to correspond, unless otherwise indicated, toany component or structure which performs the specified function of thedescribed component (e.g., that is functionally equivalent), even thoughnot structurally equivalent to the disclosed structure which performsthe function in the herein illustrated exemplary implementations of thedisclosure. In addition, while a particular feature can have beendisclosed with respect to only one of several implementations, suchfeature can be combined with one or more other features of the otherimplementations as can be desired and advantageous for any given orparticular application.

What is claimed is:
 1. An apparatus configured to be employed in a userequipment (UE) for a new radio (NR) network comprising: one or moreprocessors configured to: receive, from a network slice customer (NSC),an NSC Service ID that associates the NSC with a communication service;receive, from a network slice provider (NSP), a UE route selectionpolicy (URSP) comprising a traffic descriptor comprising the NSC ServiceID and a rule that associates the NSC Service ID with a single networkslice selection assistance information (S-NSSAI); and in response todetecting an execution of an application of the communication service,route data traffic to a network slice instance of a network slice as aservice (NSaaS) based on the NSC Service ID from the NSC and the S-NSSAIassociated with the NSC Service ID according to the URSP from the NSP.2. The apparatus of claim 1, wherein the one or more processors arefurther configured to: associate the NSC Service ID to a singleapplication of the communication service based on a service ID of theNSC Service ID.
 3. The apparatus of claim 1, wherein the rule of theURSP indicates that the NSC Service ID is associated with the networkslice instance of the NSaaS based on the S-NSSAI.
 4. The apparatus ofclaim 1, wherein the one or more processors are further configured to:establish a routing session for a gaming service as the communicationservice based on an application ID of the gaming service associated withthe NSC Service ID without sharing the application ID to the NSP.
 5. Theapparatus of claim 1, wherein the NSC Service ID comprises an NSC uniqueID associated with the NSC and a service ID associated with thecommunication service provided by the NSC.
 6. The apparatus of claim 5,wherein the communication service comprises online gaming services. 7.The apparatus of claim 5, wherein the NSC unique ID identifies the NSCfrom among different NSCs.
 8. The apparatus of claim 1, wherein the oneor more processors are further configured to receive a downlink (DL)non-access stratum (NAS) transport UE policy container message toreceive the rule of the URSP that links the NSC Service ID to theS-NSSAI to enable an association of a packet data unit (PDU) sessionwith the S-NSSAI for the application of the communication service on theNSaaS.
 9. The apparatus of claim 1, wherein the rule of the URSPassociates traffic of the application to the NSC Service ID with theS-NSSAI, and further comprises at least one of: a session and servicecontinuity (SSC) mode, a preferred access type, or a data network name(DNN).
 10. The apparatus of claim 1, wherein the one or more processorsare further configured to release, suspend, or resume the data trafficon the network slice instance only by the NSC Service ID received fromthe NSC and the S-NSSAI in the traffic descriptor of the URSP receivedfrom the NSP, wherein the NSP comprises a network operator that assignsthe NSC Service ID to the NSC for the network slice instance.
 11. Theapparatus of claim 10, wherein the network slice instance is associatedwith an application service consisting of only online gaming that isindicated in the NSC Service ID received from the NSC.
 12. The apparatusof claim 1, wherein the one or more processors are further configured torepeat a registration or a binding of an application to another NSCService ID in response to changing a universal mobile telecommunicationsystem (UMTS) subscriber identity module (USIM).
 13. A method of a userequipment (UE) to perform operations via processing circuitry,comprising: receiving, from a network slice provider (NSP), a UE routeselection policy (URSP) comprising a traffic descriptor that includes anetwork slice customer (NSC) Service ID; determining an applicationservice derived from the NSC Service ID; determining a single networkslice selection assistance information (S-NSSAI) from the URSP; andlinking the application service to a network slice based on the NSCService ID and the S-NSSAI.
 14. The method of claim 13, furthercomprising: receiving the NSC Service ID from a network slice customer(NSC) that identifies the application service and the NSC providing theapplication service to the UE with the network slice.
 15. The method ofclaim 13, further comprising: in response to detecting initiation of anapplication of the application service, routing traffic to the networkslice based on the NSC Service ID associated with the S-NSSAI withoutsharing an application identifier of the application with the NSP. 16.The method of claim 13, further comprising: determining from the NSCService ID an NSC unique ID; and determining the application servicefrom a service ID of the NSC Service ID, wherein the NSC Service IDenables an association of the NSC with the application service for thenetwork slice.
 17. The method of claim 13, further comprising:determining whether the NSC Service ID is associated with an onlinegaming service based on a service ID of the NSC Service ID; determiningwhether an application ID associated with the online gaming servicematches a URSP rule of the URSP in response to an initiation of theonline gaming service; determining whether an existing packet data unit(PDU) session matches a route selection descriptor of a trafficdescriptor that comprises the NSC Service ID and the S-NSSAI; inresponse to a determination that the NSC Service ID is associated withthe online gaming service, a match of the application ID with the URSPrule of the URSP, and the existing PDU session matching the routeselection descriptor, associating the online gaming service to theexisting PDU session on the network slice that is associated with theS-NSSAI.
 18. An apparatus configured to be employed in a user equipment(UE) comprising: one or more processors configured to: receive, from anetwork slice provider (NSP), a UE route selection policy (URSP) thatassociates a network slice customer (NSC) Service ID to a trafficdescriptor; determine a single network slice selection assistanceinformation (S-NSSAI) from the URSP; and associate an applicationservice to a network slice based on the NSC Service ID and the S-NSSAIto operate an application that includes the application service on thenetwork slice.
 19. The apparatus of claim 18, wherein the one or moreprocessors are further configured to determine the application servicederived from an NSC service ID in the NSC Service ID from an NSC entitythat obtained management of the network slice from the NSP as a networkoperator.
 20. The apparatus of claim 18, wherein the URSP comprises aURSP rule that associates the NSC Service ID of the NSC with theS-NSSAI.